fix(import): support for nested namespace packages #1805
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
If multiple directories in sys.path provide a nested namespace package, then jedi would only visit the first directory which
contained the package. Fix this by saving the remaining path list in the ImplicitNamespaceValue and add a test for it.
Added test namespace packages to demonstrate the failure:
namespace1/ namespace1/pkg1 namespace1/pkg1/pkg2 namespace1/pkg1/pkg2/mod1.py namespace2 namespace2/pkg1 namespace2/pkg1/pkg2 namespace2/pkg1/pkg2/mod2.py
If both namespace1 and namespace2 are added to sys path, then jedi sees only mod1 without the fix. After the fix it correctly sees both mod1 and mod2.